docs: update memory leak debugging skill#2330
Open
mturac wants to merge 1 commit into
Open
Conversation
mturac
force-pushed
the
izon/update-memory-leak-skill
branch
8 times, most recently
from
237b7f7 to
709080a
Compare
Author
|
Validation refreshed on the current head Local validation: git diff --check origin/main...HEAD
npm run check-format
npm run buildAll pass locally. The current GitHub checks are also green across the visible Node 22/24/26 test matrix on macOS, Ubuntu, and Windows, plus the required format, docs, title, check-changes, and CLA checks. |
mturac
force-pushed
the
izon/update-memory-leak-skill
branch
from
709080a to
d36463d
Compare
Author
|
Rebased this branch onto the current Validation on the rebased head: git diff --check origin/main...HEAD
npm run check-format
npm run test -- --test-concurrency=1 --retryAll pass locally. |
mturac
force-pushed
the
izon/update-memory-leak-skill
branch
from
d36463d to
7d67c47
Compare
Lightning00Blade
approved these changes
Jul 10, 2026
Lightning00Blade
left a comment
Lightning00Blade
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for the PR!
FYI changed the closes to issue, so we keep it open while we do other changes as well.
| - **Prefer MCP memory tools:** Do NOT attempt to read raw `.heapsnapshot` files directly, as they are extremely large and will consume too many tokens. Use the Chrome DevTools MCP heap snapshot tools to summarize, compare, and inspect snapshots. | ||
| - **Isolate the Leak:** Determine if the leak is in the browser (client-side) or Node.js (server-side). | ||
| - **Common Culprits:** Look for detached DOM nodes, unhandled closures, global variables, event listeners not being removed, and caches growing unbounded. _Note: Detached DOM nodes are sometimes intentional caches; always ask the user before nulling them._ | ||
| - **Close Loaded Snapshots:** Heap snapshots can be large. Use `close_heapsnapshot` after inspecting a file to release memory held by the MCP server. |
Collaborator
There was a problem hiding this comment.
Suggested change
| - **Close Loaded Snapshots:** Heap snapshots can be large. Use `close_heapsnapshot` after inspecting a file to release memory held by the MCP server. | |
| - **Close Loaded Snapshots:** After completing you full investigation use `close_heapsnapshot` to free up memory on the MCP server. |
I think this may be a little bit better as the first one can be interpreted as release after every tool call, which will effectively re-parse a heapsnapshot.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Issue #2329.
Validation
git diff --check origin/main...HEADnpm run check-format